Dynamic checkout button apparatuses, methods and systems

ABSTRACT

The DYNAMIC CHECKOUT BUTTON APPARATUSES, METHODS AND SYSTEMS (“DCB”) transforms product page checkout request input and user identification input via DCB components such as offer/discount determination component and checkout button embedding component, into dynamic checkout button outputs.

This application claims priority to U.S. provisional patent applicationSer. No. 62/021,187, filed Jul. 6, 2014, entitled “Dynamic CheckoutButton Apparatuses, Methods and Systems.” The entire contents of theaforementioned applications are expressly incorporated by referenceherein.

This application for letters patent disclosure document describesinventive aspects directed at various novel innovations (hereinafter“disclosure”) and contains material that is subject to copyright, maskwork, and/or other intellectual property protection. The respectiveowners of such intellectual property have no objection to the facsimilereproduction of the disclosure by anyone as it appears in publishedPatent Office file/records, but otherwise reserve all rights.

FIELD

The present innovations are directed generally to e-commerce and digitalwallets, and more particularly, to DYNAMIC CHECKOUT BUTTON APPARATUSES,METHODS AND SYSTEMS.

BACKGROUND

Consumers using the World Wide Web browse product listings of merchantsand make purchases on selected products. Discounts are offered toconsumers for their purchases. Consumer may use several payment accountsbut consumers often are confused over which account to use or whichimage represents which card.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying appendices and/or drawings illustrate variousnon-limiting, example, innovative aspects in accordance with the presentdescriptions:

FIGS. 1A-1B show block diagrams illustrating example embodiments of theDCB;

FIG. 2 shows a block diagram illustrating example data flow in someembodiments of the DCB;

FIG. 3 shows a logic flow diagram illustrating example component in someembodiments of the DCB;

FIGS. 4-7 show additional example embodiments of the DCB;

FIG. 8 shows a block diagram illustrating embodiments of a DCBcontroller.

The leading number of each reference number within the drawingsindicates the figure in which that reference number is introduced and/ordetailed. As such, a detailed discussion of reference number 101 wouldbe found and/or introduced in FIG. 1. Reference number 201 is introducedin FIG. 2, etc.

DETAILED DESCRIPTION DCB

The DYNAMIC CHECKOUT BUTTON APPARATUSES, METHODS AND SYSTEMS (“DCB”)transforms inputs such as product page checkout request and useridentification input (e.g., 211) via DCB components such asoffer/discount determination component 841 and checkout button embeddingcomponent 842, into dynamic checkout button (e.g., 265) outputs. FIG. 1Ashows a block diagram illustrating example embodiments of the DCB. Insome embodiments, the DCB may determine what type is the user 105. Ifthe user is a new user, the DCB may display the wallet checkout buttonwith offers targeted towards new customers 110, e.g., get 25% off 115.If the user is an existing and active user, the DCB may display checkoutbutton with offers targeted towards existing/active customers 130, e.g.,get 10% off 135. If the user is an existing but dormant user, the DCBmay display checkout button with offers targeted towards old/inactivecustomers 120, e.g., get free shipping when purchase 125.

FIG. 1B shows a block diagram illustrating example offers/discountsembedded in the wallet checkout button in some embodiments of the DCB.In some embodiments, the discount/offer may come with a timer whichshows how much time left for the discount/offer to be active. Forexample, it may show “time left to checkout with 40% off is 10 minutes.”150 And time left may count down 155. The discount/offer may also changeas the time counts down. For example, the discount may change from 35%off at 7 minutes 160 to 30% off at 6 minutes 165, and 25% off at 5minutes 170, etc. In some embodiments, the discount/offer may also becustomizable and user specific, as the DCB may have access to the user'swallet account which stores the user's profile information, paymentmethods information, shipping address, and/or the like. For example, itmay display a message like “Hi John, checkout now and get 3000 points toyour Amex card.” 175 For another example, it may display a message suchas “Hi John, use your discover card and get 5% cash back on yourpurchase.” 180 The DCB may also do analytics on the merchant's site oracross the web and display such analytics that's of interest to theuser. For example, it may display a message which shows historicallowest price of the product on this merchant site 185. For anotherexample, it may display a lower price at another merchant 190.

FIG. 2 shows a block diagram illustrating example data flow in someembodiments of the DCB. In some embodiments, the user 201 (e.g.,consumer) may send a product page checkout request and useridentification input 211 to the client 202 (e.g., mobile devices,computer, Point-of-Sale, laptop, and/or the like). The client mayfurther send the product page checkout request 215 to the merchantserver 205. For example, the merchant server may provide a HTTP(S) GETmessage including an XML-formatted product page checkout request 215similar to the example listing provided below:

GET /productpagecheckoutrequest.php HTTP/1.1 Host:www.merchantserver.com Content-Type: Application/XML Content-Length: 624<?XML version = “1.0” encoding = “UTF-8”?><product_page_checkout_request> <session_ID>4NFU4RG94</session_ID><timestamp>2001-02-22 15:22:43</timestamp><wallet_login_username>jsmith@wallet.com</wallet_username><wallet_login_password>xxxxxx<wallet_login_password><merchant_ID>www.macys.com</merchant_ID> <client_details><client_IP>192.168.23.126</client_IP><client_type>smartphone</client_type> <client_model>HTCHero</client_model> <OS>Android 2.2</OS><app_installed_flag>true</app_installed_flag> </client_details><product_info> <cart_id>45234</card_id> <product_id>123<product_name>book</product_name> <product_price>$12</product_price></product_id> <product_id>456 <product_name>boots</product_name><product_price>$433</product_price> </product_id> </product_info></product_page_checkout_request>

The merchant server may generate product checkout button with offer/deallink to be embedded 220. The merchant server may then send the productcheckout button with offer/deal link to be embedded 225 to the client.For example, the merchant server may provide a HTTP(S) POST messageincluding an XML-formatted product checkout button with offer/discountlink message 225 similar to the example listing provided below:

<html> <head> <script type=“text/javascript”> /** inputData is the JSONobject: {amount: .., city: .., state: ..,....} resumeFunction is whatyou call after you figured the summary details. **/ functionmyBeforeSummaryFunction(inputData, resumeFunction){ $.ajax({ url:‘/path/to/your/server/to/compute/the/summary’, data: inputData, success:function(response){ resumeFunction(response); //response should be thesummary object } }); } functionmyCallbackFunctionForVmeEvents(VmeEventType, eventData){ varMerchantTrans = eventData.merchTrans; if (VmeEventType ==“purchase.success”){ alert ( msg ); mywindow = window.open(“./checkyourorder.php?merchTrans=” + MerchantTrans,“Check your OrderID”,“width=400,height=300”); mywindow.moveTo(300,300); } } </script></head> <body> <v:init apikey=“CG6KBNNKJ5ZSSJC5XTEX”> </v:init> <v:buyapikey = “aK2Leiv89j2A1_lOn4s1” token =“12f049788f4b67dc9cc58529769fb9d2” amount = “100” currency = “USD”product-id = “cart-2536” before-summary=“myBeforeSummaryFunction”callback=“myCallbackFunction” collect-shipping=“true” process=“validate”</v:buy> <div id=“v-root”></div> <script type=“text/javascript” src=“https://sandbox-static.v.me/js/1/v-widgets.js ”></script><offer_link>link to DCB server decided offer</offer_link> </body>

Upon receiving the user identification input, the client may send theuser identification input message to 230 to the DCB server 210. The DCBserver may generate and send a query to the user database 220 for usermerchant loyalty level 235. For example, the database may be arelational database responsive to Structured Query Language (“SQL”)commands. The DCB server may execute a hypertext preprocessor (“PHP”)script including SQL commands to query the database for user merchantloyalty level. An example PHP/SQL command listing, illustratingsubstantive aspects of querying the user database 235, is providedbelow:

<?PHP header(′Content-Type: text/plain′);mysql_connect(“254.93.179.112”,$DBserver,$password); // access databaseserver mysql_select_db(“customerprofile.SQL”); // select database tableto search //create query for user merchant loyalty level data $query =“SELECT user_merchant_loyalty_level FROM CustomerProfileTable WHEREuser_ID LIKE ′%′ $123abc”; $result = mysql_query($query); // perform thesearch query mysql_close(“customerprofile.SQL”); // close databaseaccess ?>

Upon receiving the user merchant loyalty level 240, the DCB server maydetermine offer/deal dependent upon user merchant loyalty level 245. Forexample, the user merchant loyalty level data may show that the user isa new user, the DCB server may determine an offer/discount for newusers. The user merchant loyalty level data may also include userprofile information and/or any other information stored in the user'swallet. Therefore, the offer/discount message may also include anyinformation from the user's wallet. The DCB server may also determineother user specific behavior based on the information stored in wallet(e.g., 150, 155, 160, 165, 170, 175, 180, 185, 190, and/or the like).Once the DCB server determine the offer/discount 245, the DCB server maycontinue to generate corresponding offer/discount message 250. The DCBserver may further send the corresponding offer/deal message 255 to theclient. For example, the DCB server may provide a HTTP(S) POST messageincluding an XML-formatted corresponding offer/deal message 255 similarto the example listing provided below:

POST /correspondingoffermessage.php HTTP/1.1 Host: www.DCBserver.comContent-Type: Application/XML Content-Length: 624 <?XML version = “1.0”encoding = “UTF-8”?> <corresponding_offer_message><session_ID>4NFU4RG94</session_ID> <timestamp>2001-02-2215:22:43</timestamp><wallet_login_username>jsmith@wallet.com</wallet_username><wallet_login_password>xxxxxx<wallet_login_password><merchant_ID>www.macys.com</merchant_ID> <client_details><client_IP>192.168.23.126</client_IP><client_type>smartphone</client_type> <client_model>HTCHero</client_model> <OS>Android 2.2</OS><app_installed_flag>true</app_installed_flag> </client_details><offer_link>25% off</offer_link> </corresponding_offer_message>

The client may embed the offer/discount into the link position in theproduct checkout button 260, for display 265. An example HTTP messagemay be as follows:

<html> <head> <script type=“text/javascript”> /** inputData is the JSONobject: {amount: .., city: .., state: ..,....} resumeFunction is whatyou call after you figured the summary details. **/ functionmyBeforeSummaryFunction(inputData, resumeFunction){ $.ajax({ url:‘/path/to/your/server/to/compute/the/summary’, data: inputData, success:function(response){ resumeFunction(response); //response should be thesummary object } }); } functionmyCallbackFunctionForVmeEvents(VmeEventType, eventData){ varMerchantTrans = eventData.merchTrans; if (VmeEventType ==“purchase.success”){ alert ( msg ); mywindow = window.open(“./checkyourorder.php?merchTrans=” + MerchantTrans,“Check your OrderID”,“width=400,height=300”); mywindow.moveTo(300,300); } } </script></head> <body> <v:init apikey=“CG6KBNNKJ5ZSSJC5XTEX”> </v:init> <v:buyapikey = “aK2Leiv89j2A1_lOn4s1” token =“12f049788f4b67dc9cc58529769fb9d2” amount = “100” currency = “USD”product-id = “cart-2536” before-summary=“myBeforeSummaryFunction”callback=“myCallbackFunction” collect-shipping=“true” process=“validate”</v:buy> <div id=“v-root”></div> <script type=“text/javascript” src=“https://sandbox-static.v.me/js/1/v-widgets.js ”></script><offer_link>25% off</offer_link> </body>

FIG. 3 shows a logic flow diagram illustrating example component in someembodiments of the DCB. In some embodiments, the client may send tomerchant server a product page checkout request 301. The merchant servermay determine if the product is available 305. If the product isavailable, the merchant server may generate and send to client a productcheckout button with link to the offer/discount to be embedded 310. Ifthe client also receives user identification input 340 from the user,the client may send the user identification input to the DCB server 350.The DCB server may generate and send to user database a query for usermerchant loyalty level data 355. Upon receiving the user merchantloyalty level data 360, the DCB server may determine offer/discountdependent upon user merchant loyalty level 365. The DCB server maygenerate and send to client corresponding offer/discount message 370.Once the client receives the product checkout button with link to theoffer/discount to be embedded from the merchant 315, and thecorresponding offer/discount message from the DCB server 370, the clientmay embed the offer/discount into the link position in the productcheckout button 320. Once the user is ready to checkout, the user maysend the checkout request to the client 325 and the DCB server mayprocess transaction with the determined offer/discount 330. If theclient does not receive user identification input 340, the DCB servermay generate and send to client log-in unsuccessfully message 345. Ifthe product is not available 305, the merchant may generate and send toclient product unavailable message 335 and end the process.

FIGS. 4 and 5 illustrate the wide scope of the systems and methodsdescribed herein. As shown in FIGS. 4 and 5, the systems and methods canbe configured to have many different types of checkout buttons used inthe processing described above. These include, but are not limited todynamic texts; dynamic images (including photos (e.g., photo of theconsumer, photo of a favorite pet, etc.), card art, product images, orany other image or images); dynamic colors; dynamic vignettes; dynamictimers/calendars/reminders; moving images (images change over time),video, etc.

FIG. 4 depicts dynamic images at 410 including card art and other typesof dynamic images. As shown in FIG. 4, the card art of the consumer'sdefault card is placed on the checkout button when the system recognizesthe consumer (either by cookie, device fingerprint, etc.) and theconsumer has a type of “remember me” capability enabled. If theseconditions are satisfied in this example, the system will serve a buttonback as depicted in FIG. 4. The gray card and swoosh (upper checkoutbutton in FIG. 4) is the unrecognized button, and the one with the goldcard (lower checkout button in FIG. 4) represents where the recognizeddefault card art would go. The card art could be, for example, theconsumer's B of A Rewards Card. In some embodiments, the card art mayrepresent which account of several accounts a user is using for thepresent transaction. For example, a user may have a B of A Rewards Cardand a Local Bank Card and the card art may visibly represent which cardis being used for a particular transaction.

In some embodiments, a user may be able to select the art that isdisplayed as part of the transaction to make it easier to determinewhich account is being used for a transaction. For example, B of A mayhave card art available which replicates the look of a B of A card inpossession of the user. In addition, a user may be able to select orcreate additional card art that represents an account. An older user maywish to have larger lettering for example and the lettering may bemodifiable by a user. Another user may wish for a first card to becolored red indicating that the card already has a high balance andshould not be used and another card may be colored green indicating thecard does not have a balance and should be used.

In yet a further embodiment, the card art may indicate the balance inthe account related to the payment device or card. As an example, a usermay set balance limits and if the amount in an account is over or underthe limit, the card art may change. The threshold may be set by the useror may be set by the issuer or may be set by an authority and thethreshold may use real time communication and account data to set theappearance to indicate a current status of one or more of the accountsto a user.

In yet another embodiment, the card art may indicate the results of analgorithm that analyzes a variety of factors to recommend one paymentaccount over another. The factors could include the retailer, the typeof good or service to be purchase, the price of the good or service, therewards offered for using each payment account for different goods orservices at different vendors, etc. As a more specific example, if theuser wants to maximize the cash back from payment devices and the useris buying gasoline, the algorithm may review the various accounts of theuser to determine which account would result in the largest cash backreward.

The card art may also include additional computer executableinstructions that may affect the display in the button. For example, thecomputer executable instructions may also include instructions for thecard art to flash, move, change color, change in size or make a sound.For example, as the user swipes to pay, the size of the card art mayincrease or a given sound may play. The display change may be userselected or may be selected by the card issuer, the issuing bank, etc.

FIG. 5 depicts other non-limiting examples of dynamic images at 510.These include discount information that can change over time. Forexample, the discount may be a 25% a first point in time but at adifferent discount level at a subsequent period in time. As anotherexample, information that dynamically changes over time can be insertedinto the checkout button including not only what the price or discountmay be, but also the specific store or website containing such an offer.The checkout button and further include a continuously updated clock(e.g., a five-minute, one minute, 15 second interval). Still further, acheckout button can be customized to include personal information suchas the user's name as well as earning rewards (e.g., points, freeshipping, etc.) by the user selecting the checkout button. Customizationin this way operates as a further enticement for the user to effect apurchase via the checkout button.

FIG. 6 depicts at 610 that checkout buttons can be supported via manydifferent types of end touchpoints (e.g., web, mobile, wearables,kiosks, cash registers, other touchscreen devices, etc). To help inachieving personalization at these touchpoints, information can beobtained from various sources. Sources can include what information theuser has already provided to an issuer and/or merchant. In somesituations, information already stored at the issuer and/or merchantservers can be combined in order to derive the proper personalinformation (e.g., textual information, image information, etc.) to beinserted into a checkout button. Other sources of information that canbe used independently or in conjunction with the aforementioned includeinformation stored in cookies on the user's device. Cookies can includethose that track user's shopping behavior across one or moreshopping-related or other type of websites.

For example user-specific information can be obtained so that theperson's purchase card(s), username, or other specific information canbe utilized in dynamically creating a checkout button. Othercustomizations can include analyzing the purchase history of the userand determining what products the customer has a higher probability ofpurchasing. As another example, the system can determine that the userfrequents the merchant's website and therefore qualifies to have abetter offer placed in the checkout button. In other situations, thedeeper the relationship between the user and/or the merchant and/or theissuer, the more user-specific and/or generous offers/data can be placedin the checkout button.

Code to enable obtaining merchant information to display in the buttonmay be as follows:

var r = new XMLHttpRequest( ), url; url = locationOrigin( ) +‘/wallet-services-web/merchant?profileOwner=’ +_param(‘externalClientId’) + ‘&profileName=’ +_param(‘externalProfileId’); (this is the api for getting the merchant'sinformation) r.open(‘GET’, url, true);r.setRequestHeader(‘Accept’,‘application/json’);r.setRequestHeader(‘Content-type’,‘application/json’);r.setRequestHeader(‘API_KEY’, _param(‘apikey’));r.setRequestHeader(‘X-MERCHANT-API-KEY’, _param(‘apikey’));r.setRequestHeader(‘X-CORRELATION-ID’, ‘<%= response.getHeader(“X-CORRELATION-ID”) %>’); r.onreadystatechange = function( ) { if(r.readyState == 4) { if (r.status === 401) { <% /* if not active, hidebutton (by sending postMessage) */ %> // have to send it with thisadmittedly odd format to match our existing // post-message handling inthe wrapper post_message.js window.parent.postMessage(‘hide--{ }’,postMessageTarget); (A hidden button would not be visible to users) }else if (r.status === 400 ∥ r.status === 404) {window.parent.postMessage(‘lockButton--{ }’, postMessageTarget); (Alocked button would be greyed out but visible to users) } else if(r.status === 200) { (Merchant is active, api key is valid, so renderthe dynamic button) <% /* send some merchant config params back to sdk,which will pass them into checkout widget via the url */ %>if(browserLocale){ window.parent.postMessage(‘merchantConfig--’ +r.responseText+‘--{ }--’+‘{“vInitRequest”:{“browserLocale”:“‘+browserLocale+’”}}’,postMessageTarget); } else {window.parent.postMessage(‘merchantConfig--’ + r.responseText,postMessageTarget); } } } }; r.send( );

In some embodiments, a decision may be made whether to render the buttonor hide the button depending on a response from a wallet server. Forexample, if card art is available, it may be displayed and if there isno card art, the button image may be a default image. Sample computerexecutable instructions to enable the render or hide the art in thebutton decision may be as follows:

var _lockedButtonPathSmall =′checkout-widget/resources/img/integration/v1/locked-button- s.png′,_lockedButtonPathMedium =′checkout-widget/resources/img/integration/v1/locked-button- m.png′,_lockedButtonPathLarge =′checkout-widget/resources/img/integration/v1/locked-button- l.png′,(for showing a locked button to the user) _lockButton =function(message, handleClick) { var images =document.getElementsByTagName(′img′), vButtonPattern = /\bv-button\b/,clickHandler = function( ) { window.alert(message); }, newWidth, i; for(i = 0; i < images.length; i++) { if(vButtonPattern.test(images[i].className)) { newWidth =_param(′size′,images[i].src) ∥ 213; if (handleClick) { images[i].onclick= clickHandler; } images[i].title = message; images[i].src =_getAssetsDomain( ); switch (true) { (determine correct locked buttonimage to show based on merchant's preference via a “size” parametermerchant passes to us) case parseInt(newWidth, 10) < 213: images[i].src+= _lockedButtonPathSmall; break; case parseInt(newWidth, 10) >= 425:images[i].src += _lockedButtonPathLarge; break; default: images[i].src+= _lockedButtonPathMedium; } } } _isLocked = true; }, _hideButton =function( ) { var buttonElements =window.parent.document.querySelectorAll(′.v-button′), buttonElement,buttonIndex; for (buttonIndex = 0; buttonIndex < buttonElements.length;buttonIndex++) { buttonElement = buttonElements[buttonIndex];buttonElement.style.visibility = ′hidden′; } }, _receiveMessage =function(event) { var message = event.data.split(′--′), data = { },error, sdkOptions, hideWidget, v1Merchant; if (message.length > 1) {data = JSON.parse(message[1]); if (message.length > 2) { error =JSON.parse(message[2]); } if (message.length > 3) { sdkOptions =JSON.parse(message[3]); } } if (data.merchantType !== ′v1′) {data.vInitRequest = _merchantOpts; } delete data.merchantType; if(event.origin === _getDomain( )) { switch(message[0]) { case ″success″ :try { _successCallback(data); }finally{ _hide( ); } break; case ″cancel″: try { _cancelCallback(data); }finally{ if (hideWidget) { _hide( ); } }break; case ″error″ : try { _errorCallback(data, error); }finally{ if(hideWidget) { _hide( ); } } break; case ″lock″ : _errorCallback(data);if (hideWidget) { _hide( ); } break; case ″hide″ : _hideButton( );break; case ″lockButton″ : _lockButton(_integrationError, false); break;case ″merchantConfig″: if(sdkOptions.vInitRequest &&sdkOptions.vInitRequest.browserLocale){ data.vInitRequest.browserLocale= sdkOptions.vInitRequest.browserLocale; } _merchantConfig(data); break;} } }, V.setOptions = function(options) { var buttons =document.querySelectorAll(′.v-button′), i; for (i = 0; i <buttons.length; i++) { buttons[i].src = _getAssetsDomain( ) + ′/wallet-services-web/xo/button.png′; (if we are going to render anactive button then we make another call to Wallet Services Back End toget the image) buttons[i].title = ″; } // need to pass this to iframedue to security policy options.parentUrl = window.location.href;_merchantOpts = options; _getMerchantConfig(options);  };

Logically, the computer executable instructions may be embodied in apurpose built processor or may be executed by another processor that isphysically configured according to the computer executable instructions.

As shown at 710 in FIG. 7, the content of the checkout button can bebased on many different types of data. For example, the time andlocation of the user can also be ascertained to supplement theinformation that is to be processed in order to generate thetextual/image data for insertion into a checkout button. Thetextual/image data can also be tailored to the specific channel of theuser (e.g., the user is on a mobile phone versus the user being at akiosk or at a merchant-operated cash register).

Additionally, a greater degree of branding can be placed in the checkoutbuttons, such as colors that help identify the merchant or other companyor logos of the merchant or other company. Because “real estate” is at apremium for a checkout button (e.g., a two inch-by-one inch sizedcheckout button), the data (e.g., images, text, etc.) can be tailored tothe specific merchant and/or user in order to enhance the probabilitythat the user will click on the checkout button.

DCB Controller

FIG. 8 shows a block diagram illustrating embodiments of a DCBcontroller. In this embodiment, the DCB controller 801 may serve toaggregate, process, store, search, serve, identify, instruct, generate,match, and/or facilitate interactions with a computer through variousbi-directional linking technologies, and/or other related data.

Typically, users, which may be people and/or other systems, may engageinformation technology systems (e.g., computers) to facilitateinformation processing. In turn, computers employ processors to processinformation; such processors 803 may be referred to as centralprocessing units (CPU). One form of processor is referred to as amicroprocessor. CPUs use communicative circuits to pass binary encodedsignals acting as instructions to enable various operations. Theseinstructions may be operational and/or data instructions containingand/or referencing other instructions and data in various processoraccessible and operable areas of memory 829 (e.g., registers, cachememory, random access memory, etc.). Such communicative instructions maybe stored and/or transmitted in batches (e.g., batches of instructions)as programs and/or data components to facilitate desired operations.These stored instruction codes, e.g., programs, may engage the CPUcircuit components and other motherboard and/or system components toperform desired operations. One type of program is a computer operatingsystem, which, may be executed by CPU on a computer; the operatingsystem enables and facilitates users to access and operate computerinformation technology and resources. Some resources that may beemployed in information technology systems include: input and outputmechanisms through which data may pass into and out of a computer;memory storage into which data may be saved; and processors by whichinformation may be processed. These information technology systems maybe used to collect data for later retrieval, analysis, and manipulation,which may be facilitated through a database program. These informationtechnology systems provide interfaces that allow users to access andoperate various system components.

In one embodiment, the DCB controller 801 may be connected to and/orcommunicate with entities such as, but not limited to: one or more usersfrom user input devices 811; peripheral devices 812; an optionalcryptographic processor device 828; and/or a communications network 813.

Networks are commonly thought to comprise the interconnection andinteroperation of clients, servers, and intermediary nodes in a graphtopology. It should be noted that the term “server” as used throughoutthis application refers generally to a computer, other device, program,or combination thereof that processes and responds to the requests ofremote users across a communications network. Servers serve theirinformation to requesting “clients.” The term “client” as used hereinrefers generally to a computer, program, other device, user and/orcombination thereof that is capable of processing and making requestsand obtaining and processing any responses from servers across acommunications network. A computer, other device, program, orcombination thereof that facilitates, processes information andrequests, and/or furthers the passage of information from a source userto a destination user is commonly referred to as a “node.” Networks aregenerally thought to facilitate the transfer of information from sourcepoints to destinations. A node specifically tasked with furthering thepassage of information from a source to a destination is commonly calleda “router.” There are many forms of networks such as Local Area Networks(LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks(WLANs), etc. For example, the Internet is generally accepted as beingan interconnection of a multitude of networks whereby remote clients andservers may access and interoperate with one another.

The DCB controller 801 may be based on computer systems that maycomprise, but are not limited to, components such as: a computersystemization 802 connected to memory 829.

Computer Systemization

A computer systemization 802 may comprise a clock 830, centralprocessing unit (“CPU(s)” and/or “processor(s)” (these terms are usedinterchangeable throughout the disclosure unless noted to the contrary))803, a memory 829 (e.g., a read only memory (ROM) 806, a random accessmemory (RAM) 805, etc.), and/or an interface bus 807, and mostfrequently, although not necessarily, are all interconnected and/orcommunicating through a system bus 804 on one or more (mother)board(s)802 having conductive and/or otherwise transportive circuit pathwaysthrough which instructions (e.g., binary encoded signals) may travel toeffectuate communications, operations, storage, etc. The computersystemization may be connected to a power source 886; e.g., optionallythe power source may be internal. Optionally, a cryptographic processor826 and/or transceivers (e.g., ICs) 874 may be connected to the systembus. In another embodiment, the cryptographic processor and/ortransceivers may be connected as either internal and/or externalperipheral devices 812 via the interface bus I/O. In turn, thetransceivers may be connected to antenna(s) 875, thereby effectuatingwireless transmission and reception of various communication and/orsensor protocols; for example the antenna(s) may connect to: a TexasInstruments WiLink WL1283 transceiver chip (e.g., providing 802.11n,Bluetooth 3.0, FM, global positioning system (GPS) (thereby allowing DCBcontroller to determine its location)); Broadcom BCM4329FKUBGtransceiver chip (e.g., providing 802.11n, Bluetooth 2.1+EDR, FM, etc.);a Broadcom BCM4750IUB8 receiver chip (e.g., GPS); an InfineonTechnologies X-Gold 618-PMB9800 (e.g., providing 2G/3G HSDPA/HSUPAcommunications); and/or the like. The system clock typically has acrystal oscillator and generates a base signal through the computersystemization's circuit pathways. The clock is typically coupled to thesystem bus and various clock multipliers that will increase or decreasethe base operating frequency for other components interconnected in thecomputer systemization. The clock and various components in a computersystemization drive signals embodying information throughout the system.Such transmission and reception of instructions embodying informationthroughout a computer systemization may be commonly referred to ascommunications. These communicative instructions may further betransmitted, received, and the cause of return and/or replycommunications beyond the instant computer systemization to:communications networks, input devices, other computer systemizations,peripheral devices, and/or the like. It should be understood that inalternative embodiments, any of the above components may be connecteddirectly to one another, connected to the CPU, and/or organized innumerous variations employed as exemplified by various computer systems.

The CPU comprises at least one high-speed data processor adequate toexecute program components for executing user and/or system-generatedrequests. Often, the processors themselves will incorporate variousspecialized processing units, such as, but not limited to: integratedsystem (bus) controllers, memory management control units, floatingpoint units, and even specialized processing sub-units like graphicsprocessing units, digital signal processing units, and/or the like.Additionally, processors may include internal fast access addressablememory, and be capable of mapping and addressing memory 829 beyond theprocessor itself; internal memory may include, but is not limited to:fast registers, various levels of cache memory (e.g., level 1, 2, 3,etc.), RAM, etc. The processor may access this memory through the use ofa memory address space that is accessible via instruction address, whichthe processor can construct and decode allowing it to access a circuitpath to a specific memory address space having a memory state. The CPUmay be a microprocessor such as: AMD's Athlon, Duron and/or Opteron;ARM's application, embedded and secure processors; IBM and/or Motorola'sDragonBall and PowerPC; IBM's and Sony's Cell processor; Intel'sCeleron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or thelike processor(s). The CPU interacts with memory through instructionpassing through conductive and/or transportive conduits (e.g., (printed)electronic and/or optic circuits) to execute stored instructions (i.e.,program code) according to conventional data processing techniques. Suchinstruction passing facilitates communication within the DCB controllerand beyond through various interfaces. Should processing requirementsdictate a greater amount speed and/or capacity, distributed processors(e.g., Distributed DCB), mainframe, multi-core, parallel, and/orsuper-computer architectures may similarly be employed. Alternatively,should deployment requirements dictate greater portability, smallerPersonal Digital Assistants (PDAs) may be employed.

Depending on the particular implementation, features of the DCB may beachieved by implementing a microcontroller such as CAST's R8051XC2microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or thelike. Also, to implement certain features of the DCB, some featureimplementations may rely on embedded components, such as:Application-Specific Integrated Circuit (“ASIC”), Digital SignalProcessing (“DSP”), Field Programmable Gate Array (“FPGA”), and/or thelike embedded technology. For example, any of the DCB componentcollection (distributed or otherwise) and/or features may be implementedvia the microprocessor and/or via embedded components; e.g., via ASIC,coprocessor, DSP, FPGA, and/or the like. Alternately, someimplementations of the DCB may be implemented with embedded componentsthat are configured and used to achieve a variety of features or signalprocessing.

Depending on the particular implementation, the embedded components mayinclude software solutions, hardware solutions, and/or some combinationof both hardware/software solutions. For example, DCB features discussedherein may be achieved through implementing FPGAs, which are asemiconductor devices containing programmable logic components called“logic blocks”, and programmable interconnects, such as the highperformance FPGA Virtex series and/or the low cost Spartan seriesmanufactured by Xilinx. Logic blocks and interconnects can be programmedby the customer or designer, after the FPGA is manufactured, toimplement any of the DCB features. A hierarchy of programmableinterconnects allow logic blocks to be interconnected as needed by theDCB system designer/administrator, somewhat like a one-chip programmablebreadboard. An FPGA's logic blocks can be programmed to perform theoperation of basic logic gates such as AND, and XOR, or more complexcombinational operators such as decoders or mathematical operations. Inmost FPGAs, the logic blocks also include memory elements, which may becircuit flip-flops or more complete blocks of memory. In somecircumstances, the DCB may be developed on regular FPGAs and thenmigrated into a fixed version that more resembles ASIC implementations.Alternate or coordinating implementations may migrate DCB controllerfeatures to a final ASIC instead of or in addition to FPGAs. Dependingon the implementation all of the aforementioned embedded components andmicroprocessors may be considered the “CPU” and/or “processor” for theDCB.

Power Source

The power source 886 may be of any standard form for powering smallelectronic circuit board devices such as the following power cells:alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium,solar cells, and/or the like. Other types of AC or DC power sources maybe used as well. In the case of solar cells, in one embodiment, the caseprovides an aperture through which the solar cell may capture photonicenergy. The power cell 886 is connected to at least one of theinterconnected subsequent components of the DCB thereby providing anelectric current to all subsequent components. In one example, the powersource 886 is connected to the system bus component 804. In analternative embodiment, an outside power source 886 is provided througha connection across the I/O 808 interface. For example, a USB and/orIEEE 1394 connection carries both data and power across the connectionand is therefore a suitable source of power.

Interface Adapters

Interface bus(ses) 807 may accept, connect, and/or communicate to anumber of interface adapters, conventionally although not necessarily inthe form of adapter cards, such as but not limited to: input outputinterfaces (I/O) 808, storage interfaces 809, network interfaces 810,and/or the like. Optionally, cryptographic processor interfaces 827similarly may be connected to the interface bus. The interface busprovides for the communications of interface adapters with one anotheras well as with other components of the computer systemization.Interface adapters are adapted for a compatible interface bus. Interfaceadapters conventionally connect to the interface bus via a slotarchitecture. Conventional slot architectures may be employed, such as,but not limited to: Accelerated Graphics Port (AGP), Card Bus,(Extended) Industry Standard Architecture ((E)ISA), Micro ChannelArchitecture (MCA), NuBus, Peripheral Component Interconnect (Extended)(PCI(X)), PCI Express, Personal Computer Memory Card InternationalAssociation (PCMCIA), and/or the like.

Storage interfaces 809 may accept, communicate, and/or connect to anumber of storage devices such as, but not limited to: storage devices814, removable disc devices, and/or the like. Storage interfaces mayemploy connection protocols such as, but not limited to: (Ultra)(Serial) Advanced Technology Attachment (Packet Interface) ((Ultra)(Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE),Institute of Electrical and Electronics Engineers (IEEE) 1394, fiberchannel, Small Computer Systems Interface (SCSI), Universal Serial Bus(USB), and/or the like.

Network interfaces 810 may accept, communicate, and/or connect to acommunications network 813. Through a communications network 813, theDCB controller is accessible through remote clients 833 b (e.g.,computers with web browsers) by users 833 a. Network interfaces mayemploy connection protocols such as, but not limited to: direct connect,Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or thelike), Token Ring, wireless connection such as IEEE 802.11a-x, and/orthe like. Should processing requirements dictate a greater amount speedand/or capacity, distributed network controllers (e.g., DistributedDCB), architectures may similarly be employed to pool, load balance,and/or otherwise increase the communicative bandwidth required by theDCB controller. A communications network may be any one and/or thecombination of the following: a direct interconnection; the Internet; aLocal Area Network (LAN); a Metropolitan Area Network (MAN); anOperating Missions as Nodes on the Internet (OMNI); a secured customconnection; a Wide Area Network (WAN); a wireless network (e.g.,employing protocols such as, but not limited to a Wireless ApplicationProtocol (WAP), I-mode, and/or the like); and/or the like. A networkinterface may be regarded as a specialized form of an input outputinterface. Further, multiple network interfaces 810 may be used toengage with various communications network types 813. For example,multiple network interfaces may be employed to allow for thecommunication over broadcast, multicast, and/or unicast networks.

Input Output interfaces (I/O) 808 may accept, communicate, and/orconnect to user input devices 811, peripheral devices 812, cryptographicprocessor devices 828, and/or the like. I/O may employ connectionprotocols such as, but not limited to: audio: analog, digital, monaural,RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE1394a-b, serial, universal serial bus (USB); infrared; joystick;keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface:Apple Desktop Connector (ADC), BNC, coaxial, component, composite,digital, Digital Visual Interface (DVI), high-definition multimediainterface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like;wireless transceivers: 802.11a/b/g/n/x; Bluetooth; cellular (e.g., codedivision multiple access (CDMA), high speed packet access (HSPA(+)),high-speed downlink packet access (HSDPA), global system for mobilecommunications (GSM), long term evolution (LTE), WiMax, etc.); and/orthe like. One typical output device may include a video display, whichtypically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display(LCD) based monitor with an interface (e.g., DVI circuitry and cable)that accepts signals from a video interface, may be used. The videointerface composites information generated by a computer systemizationand generates video signals based on the composited information in avideo memory frame. Another output device is a television set, whichaccepts signals from a video interface. Typically, the video interfaceprovides the composited video information through a video connectioninterface that accepts a video display interface (e.g., an RCA compositevideo connector accepting an RCA composite video cable; a DVI connectoraccepting a DVI display cable, etc.).

User input devices 811 often are a type of peripheral device 512 (seebelow) and may include: card readers, dongles, finger print readers,gloves, graphics tablets, joysticks, keyboards, microphones, mouse(mice), remote controls, retina readers, touch screens (e.g.,capacitive, resistive, etc.), trackballs, trackpads, sensors (e.g.,accelerometers, ambient light, GPS, gyroscopes, proximity, etc.),styluses, and/or the like.

Peripheral devices 812 may be connected and/or communicate to I/O and/orother facilities of the like such as network interfaces, storageinterfaces, directly to the interface bus, system bus, the CPU, and/orthe like. Peripheral devices may be external, internal and/or part ofthe DCB controller. Peripheral devices may include: antenna, audiodevices (e.g., line-in, line-out, microphone input, speakers, etc.),cameras (e.g., still, video, webcam, etc.), dongles (e.g., for copyprotection, ensuring secure transactions with a digital signature,and/or the like), external processors (for added capabilities; e.g.,crypto devices 528), force-feedback devices (e.g., vibrating motors),network interfaces, printers, scanners, storage devices, transceivers(e.g., cellular, GPS, etc.), video devices (e.g., goggles, monitors,etc.), video sources, visors, and/or the like. Peripheral devices ofteninclude types of input devices (e.g., cameras).

It should be noted that although user input devices and peripheraldevices may be employed, the DCB controller may be embodied as anembedded, dedicated, and/or monitor-less (i.e., headless) device,wherein access would be provided over a network interface connection.

Cryptographic units such as, but not limited to, microcontrollers,processors 826, interfaces 827, and/or devices 828 may be attached,and/or communicate with the DCB controller. A MC68HC16 microcontroller,manufactured by Motorola Inc., may be used for and/or withincryptographic units. The MC68HC16 microcontroller utilizes a 16-bitmultiply-and-accumulate instruction in the 16 MHz configuration andrequires less than one second to perform a 512-bit RSA private keyoperation. Cryptographic units support the authentication ofcommunications from interacting agents, as well as allowing foranonymous transactions. Cryptographic units may also be configured aspart of the CPU. Equivalent microcontrollers and/or processors may alsobe used. Other commercially available specialized cryptographicprocessors include: Broadcom's CryptoNetX and other Security Processors;nCipher's nShield; SafeNet's Luna PCI (e.g., 7100) series; SemaphoreCommunications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators(e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); ViaNano Processor (e.g., L2100, L2200, U2400) line, which is capable ofperforming 500+MB/s of cryptographic instructions; VLSI Technology's 33MHz 6868; and/or the like.

Memory

Generally, any mechanization and/or embodiment allowing a processor toaffect the storage and/or retrieval of information is regarded as memory829. However, memory is a fungible technology and resource, thus, anynumber of memory embodiments may be employed in lieu of or in concertwith one another. It is to be understood that the DCB controller and/ora computer systemization may employ various forms of memory 829. Forexample, a computer systemization may be configured wherein theoperation of on-chip CPU memory (e.g., registers), RAM, ROM, and anyother storage devices are provided by a paper punch tape or paper punchcard mechanism; however, such an embodiment would result in an extremelyslow rate of operation. In a typical configuration, memory 829 willinclude ROM 806, RAM 805, and a storage device 814. A storage device 814may be any conventional computer system storage. Storage devices mayinclude a drum; a (fixed and/or removable) magnetic disk drive; amagneto-optical drive; an optical drive (i.e., Blueray, CDROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); anarray of devices (e.g., Redundant Array of Independent Disks (RAID));solid state memory devices (USB memory, solid state drives (SSD), etc.);other processor-readable storage mediums; and/or other devices of thelike. Thus, a computer systemization generally requires and makes use ofmemory.

Component Collection

The memory 829 may contain a collection of program and/or databasecomponents and/or data such as, but not limited to: operating systemcomponent(s) 815 (operating system); information server component(s) 816(information server); user interface component(s) 817 (user interface);Web browser component(s) 818 (Web browser); database(s) 819; mail servercomponent(s) 821; mail client component(s) 822; cryptographic servercomponent(s) 820 (cryptographic server); the DCB component(s) 835;offer/discount determination component 841; checkout button embeddingcomponent 842; and/or the like (i.e., collectively a componentcollection). These components may be stored and accessed from thestorage devices and/or from storage devices accessible through aninterface bus. Although non-conventional program components such asthose in the component collection, typically, are stored in a localstorage device 814, they may also be loaded and/or stored in memory suchas: peripheral devices, RAM, remote storage facilities through acommunications network, ROM, various forms of memory, and/or the like.

Operating System

The operating system component 815 is an executable program componentfacilitating the operation of the DCB controller. Typically, theoperating system facilitates access of I/O, network interfaces,peripheral devices, storage devices, and/or the like. The operatingsystem may be a highly fault tolerant, scalable, and secure system suchas: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix andUnix-like system distributions (such as AT&T's UNIX; Berkley SoftwareDistribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/orthe like; Linux distributions such as Red Hat, Ubuntu, and/or the like);and/or the like operating systems. However, more limited and/or lesssecure operating systems also may be employed such as Apple MacintoshOS, IBM OS/2, Microsoft DOS, Microsoft Windows2000/2003/3.1/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/orthe like. An operating system may communicate to and/or with othercomponents in a component collection, including itself, and/or the like.Most frequently, the operating system communicates with other programcomponents, user interfaces, and/or the like. For example, the operatingsystem may contain, communicate, generate, obtain, and/or provideprogram component, system, user, and/or data communications, requests,and/or responses. The operating system, once executed by the CPU, mayenable the interaction with communications networks, data, I/O,peripheral devices, program components, memory, user input devices,and/or the like. The operating system may provide communicationsprotocols that allow the DCB controller to communicate with otherentities through a communications network 813. Various communicationprotocols may be used by the DCB controller as a subcarrier transportmechanism for interaction, such as, but not limited to: multicast,TCP/IP, UDP, unicast, and/or the like.

Information Server

An information server component 816 is a stored program component thatis executed by a CPU. The information server may be a conventionalInternet information server such as, but not limited to Apache SoftwareFoundation's Apache, Microsoft's Internet Information Server, and/or thelike. The information server may allow for the execution of programcomponents through facilities such as Active Server Page (ASP), ActiveX,(ANSI) (Objective−) C (++), C# and/or .NET, Common Gateway Interface(CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH,Java, JavaScript, Practical Extraction Report Language (PERL), HypertextPre-Processor (PHP), pipes, Python, wireless application protocol (WAP),WebObjects, and/or the like. The information server may support securecommunications protocols such as, but not limited to, File TransferProtocol (FTP); HyperText Transfer Protocol (HTTP); Secure HypertextTransfer Protocol (HTTPS), Secure Socket Layer (SSL), messagingprotocols (e.g., America Online (AOL) Instant Messenger (AIM),Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), MicrosoftNetwork (MSN) Messenger Service, Presence and Instant Messaging Protocol(PRIM), Internet Engineering Task Force's (IETF's) Session InitiationProtocol (SIP), SIP for Instant Messaging and Presence LeveragingExtensions (SIMPLE), open XML-based Extensible Messaging and PresenceProtocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) InstantMessaging and Presence Service (IMPS)), Yahoo! Instant MessengerService, and/or the like. The information server provides results in theform of Web pages to Web browsers, and allows for the manipulatedgeneration of the Web pages through interaction with other programcomponents. After a Domain Name System (DNS) resolution portion of anHTTP request is resolved to a particular information server, theinformation server resolves requests for information at specifiedlocations on the DCB controller based on the remainder of the HTTPrequest. For example, a request such ashttp://123.124.125.126/myInformation.html might have the IP portion ofthe request “123.124.125.126” resolved by a DNS server to an informationserver at that IP address; that information server might in turn furtherparse the http request for the “/myInformation.html” portion of therequest and resolve it to a location in memory containing theinformation “myInformation.html.” Additionally, other informationserving protocols may be employed across various ports, e.g., FTPcommunications across port 21, and/or the like. An information servermay communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the information server communicates with the DCB database819, operating systems, other program components, user interfaces, Webbrowsers, and/or the like.

Access to the DCB database may be achieved through a number of databasebridge mechanisms such as through scripting languages as enumeratedbelow (e.g., CGI) and through inter-application communication channelsas enumerated below (e.g., CORBA, WebObjects, etc.). Any data requeststhrough a Web browser are parsed through the bridge mechanism intoappropriate grammars as required by the DCB. In one embodiment, theinformation server would provide a Web form accessible by a Web browser.Entries made into supplied fields in the Web form are tagged as havingbeen entered into the particular fields, and parsed as such. The enteredterms are then passed along with the field tags, which act to instructthe parser to generate queries directed to appropriate tables and/orfields. In one embodiment, the parser may generate queries in standardSQL by instantiating a search string with the proper join/selectcommands based on the tagged text entries, wherein the resulting commandis provided over the bridge mechanism to the DCB as a query. Upongenerating query results from the query, the results are passed over thebridge mechanism, and may be parsed for formatting and generation of anew results Web page by the bridge mechanism. Such a new results Webpage is then provided to the information server, which may supply it tothe requesting Web browser.

Also, an information server may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses.

User Interface

Computer interfaces in some respects are similar to automobile operationinterfaces. Automobile operation interface elements such as steeringwheels, gearshifts, and speedometers facilitate the access, operation,and display of automobile resources, and status. Computer interactioninterface elements such as check boxes, cursors, menus, scrollers, andwindows (collectively and commonly referred to as widgets) similarlyfacilitate the access, capabilities, operation, and display of data andcomputer hardware and operating system resources, and status. Operationinterfaces are commonly called user interfaces. Graphical userinterfaces (GUIs) such as the Apple Macintosh Operating System's Aqua,IBM's OS/2, Microsoft's Windows2000/2003/3.1/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix'sX-Windows (e.g., which may include additional Unix graphic interfacelibraries and layers such as K Desktop Environment (KDE), mythTV and GNUNetwork Object Model Environment (GNOME)), web interface libraries(e.g., ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, etc. interfacelibraries such as, but not limited to, Dojo, jQuery(UI), MooTools,Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any ofwhich may be used and) provide a baseline and means of accessing anddisplaying information graphically to users.

A user interface component 817 is a stored program component that isexecuted by a CPU. The user interface may be a conventional graphic userinterface as provided by, with, and/or atop operating systems and/oroperating environments such as already discussed. The user interface mayallow for the display, execution, interaction, manipulation, and/oroperation of program components and/or system facilities through textualand/or graphical facilities. The user interface provides a facilitythrough which users may affect, interact, and/or operate a computersystem. A user interface may communicate to and/or with other componentsin a component collection, including itself, and/or facilities of thelike. Most frequently, the user interface communicates with operatingsystems, other program components, and/or the like. The user interfacemay contain, communicate, generate, obtain, and/or provide programcomponent, system, user, and/or data communications, requests, and/orresponses.

Web Browser

A Web browser component 818 is a stored program component that isexecuted by a CPU. The Web browser may be a conventional hypertextviewing application such as Microsoft Internet Explorer or NetscapeNavigator. Secure Web browsing may be supplied with 128 bit (or greater)encryption by way of HTTPS, SSL, and/or the like. Web browsers allowingfor the execution of program components through facilities such asActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-inAPIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or thelike. Web browsers and like information access tools may be integratedinto PDAs, cellular telephones, and/or other mobile devices. A Webbrowser may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Mostfrequently, the Web browser communicates with information servers,operating systems, integrated program components (e.g., plug-ins),and/or the like; e.g., it may contain, communicate, generate, obtain,and/or provide program component, system, user, and/or datacommunications, requests, and/or responses. Also, in place of a Webbrowser and information server, a combined application may be developedto perform similar operations of both. The combined application wouldsimilarly affect the obtaining and the provision of information tousers, user agents, and/or the like from the DCB enabled nodes. Thecombined application may be nugatory on systems employing standard Webbrowsers.

Mail Server

A mail server component 821 is a stored program component that isexecuted by a CPU 803. The mail server may be a conventional Internetmail server such as, but not limited to sendmail, Microsoft Exchange,and/or the like. The mail server may allow for the execution of programcomponents through facilities such as ASP, ActiveX, (ANSI) (Objective−)C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes,Python, WebObjects, and/or the like. The mail server may supportcommunications protocols such as, but not limited to: Internet messageaccess protocol (IMAP), Messaging Application Programming Interface(MAPI)/Microsoft Exchange, post office protocol (POP3), simple mailtransfer protocol (SMTP), and/or the like. The mail server can route,forward, and process incoming and outgoing mail messages that have beensent, relayed and/or otherwise traversing through and/or to the DCB.

Access to the DCB mail may be achieved through a number of APIs offeredby the individual Web server components and/or the operating system.

Also, a mail server may contain, communicate, generate, obtain, and/orprovide program component, system, user, and/or data communications,requests, information, and/or responses.

Mail Client

A mail client component 822 is a stored program component that isexecuted by a CPU 803. The mail client may be a conventional mailviewing application such as Apple Mail, Microsoft Entourage, MicrosoftOutlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or thelike. Mail clients may support a number of transfer protocols, such as:IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, themail client communicates with mail servers, operating systems, othermail clients, and/or the like; e.g., it may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, information, and/or responses. Generally,the mail client provides a facility to compose and transmit electronicmail messages.

Cryptographic Server

A cryptographic server component 820 is a stored program component thatis executed by a CPU 803, cryptographic processor 826, cryptographicprocessor interface 827, cryptographic processor device 828, and/or thelike. Cryptographic processor interfaces will allow for expedition ofencryption and/or decryption requests by the cryptographic component;however, the cryptographic component, alternatively, may run on aconventional CPU. The cryptographic component allows for the encryptionand/or decryption of provided data. The cryptographic component allowsfor both symmetric and asymmetric (e.g., Pretty Good Protection (PGP))encryption and/or decryption. The cryptographic component may employcryptographic techniques such as, but not limited to: digitalcertificates (e.g., X.509 authentication framework), digital signatures,dual signatures, enveloping, password access protection, public keymanagement, and/or the like. The cryptographic component will facilitatenumerous (encryption and/or decryption) security protocols such as, butnot limited to: checksum, Data Encryption Standard (DES), EllipticalCurve Encryption (ECC), International Data Encryption Algorithm (IDEA),Message Digest 5 (MD5, which is a one way hash operation), passwords,Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption andauthentication system that uses an algorithm developed in 1977 by RonRivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA),Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS),and/or the like. Employing such encryption security protocols, the DCBmay encrypt all incoming and/or outgoing communications and may serve asnode within a virtual private network (VPN) with a wider communicationsnetwork. The cryptographic component facilitates the process of“security authorization” whereby access to a resource is inhibited by asecurity protocol wherein the cryptographic component effects authorizedaccess to the secured resource. In addition, the cryptographic componentmay provide unique identifiers of content, e.g., employing and MD5 hashto obtain a unique signature for an digital audio file. A cryptographiccomponent may communicate to and/or with other components in a componentcollection, including itself, and/or facilities of the like. Thecryptographic component supports encryption schemes allowing for thesecure transmission of information across a communications network toenable the DCB component to engage in secure transactions if so desired.The cryptographic component facilitates the secure accessing ofresources on the DCB and facilitates the access of secured resources onremote systems; i.e., it may act as a client and/or server of securedresources. Most frequently, the cryptographic component communicateswith information servers, operating systems, other program components,and/or the like. The cryptographic component may contain, communicate,generate, obtain, and/or provide program component, system, user, and/ordata communications, requests, and/or responses.

The DCB Database

The DCB database component 819 may be embodied in a database and itsstored data. The database is a stored program component, which isexecuted by the CPU; the stored program component portion configuringthe CPU to process the stored data. The database may be a conventional,fault tolerant, relational, scalable, secure database such as Oracle orSybase. Relational databases are an extension of a flat file. Relationaldatabases consist of a series of related tables. The tables areinterconnected via a key field. Use of the key field allows thecombination of the tables by indexing against the key field; i.e., thekey fields act as dimensional pivot points for combining informationfrom various tables. Relationships generally identify links maintainedbetween tables by matching primary keys. Primary keys represent fieldsthat uniquely identify the rows of a table in a relational database.More precisely, they uniquely identify rows of a table on the “one” sideof a one-to-many relationship.

Alternatively, the DCB database may be implemented using variousstandard data-structures, such as an array, hash, (linked) list, struct,structured text file (e.g., XML), table, and/or the like. Suchdata-structures may be stored in memory and/or in (structured) files. Inanother alternative, an object-oriented database may be used, such asFrontier, ObjectStore, Poet, Zope, and/or the like. Object databases caninclude a number of object collections that are grouped and/or linkedtogether by common attributes; they may be related to other objectcollections by some common attributes. Object-oriented databases performsimilarly to relational databases with the exception that objects arenot just pieces of data but may have other types of capabilitiesencapsulated within a given object. If the DCB database is implementedas a data-structure, the use of the DCB database 819 may be integratedinto another component such as the DCB component 835. Also, the databasemay be implemented as a mix of data structures, objects, and relationalstructures. Databases may be consolidated and/or distributed incountless variations through standard data processing techniques.Portions of databases, e.g., tables, may be exported and/or imported andthus decentralized and/or integrated.

In one embodiment, the database component 819 includes several tables419 a-m. A user table 819 a includes fields such as, but not limited to:a user_ID, name, home_address, work_address, telephone_number, email,merchant_ID client_id, account_id, and/or the like. The user table maysupport and/or track multiple entity accounts on a DCB. Amerchant/service provider table 819 b includes fields such as, but notlimited to: merchant_ID, merchant_name, merchant_location,merchant_address, merchant_category_code, merchant_api_key,loyalty_program_ID and/or the like. A customer profile table 819 cincludes fields such as, but not limited to: user_ID, merchant_ID,payment_card_ID, preferred_payment_type, demographics,merchant_loyalty_level, and/or the like. A permissions table 819 dincludes fields such as, but not limited to: customer_ID,transaction_execution authorization_status,confirmation_authorization_status, billing_authorization_status,subscription_payment_authorization_status, and/or the like. A paymentcard table 819 e includes fields such as, but not limited to:payment_card_id, user_id, identifier, brand, expiration_date,spending_limit, billing_address, issuer, name, nick_name,loyalty_program_ID, and/or the like. A billing agreement table 819 fincludes fields such as, but not limited to: customer_id, billing_id,billing_date, billing_amount_limit, confirmation_requirement,authentication_level, billing_authorization_status, and/or the like. Aredemption table 819 g includes fields such as, but not limited to:customer_id, loyalty_program_id, coupon_id, redemption_date,redemption_time, redemption_amount, redemption_type, transaction_id,and/or the like. A loyalty table 819 h includes fields such as, but notlimited to: loyalty_program_ID, rules, loyalty_currency_amount,loyalty_expiry_date, transaction_ID, and/or the like. A discount table819 i includes fields such as, but not limited to: discount_ID,discount_value, discount_accepted_location, discount_expiry_date, and/orthe like. A wishlist table 819 j includes fields such as, but notlimited to: wishlist_ID, merchant_ID, item_ID, and/or the like. Atransaction table 819 k includes fields such as, but not limited to:transaction_id, merchant_id, user_id, session_id, date, time,item_model, manufacturer, price, item_id, and/or the like. A productstable 819 l includes fields such as, but not limited to: product_id,merchant_id, item_id, and/or the like. An Account Balance table 819 mincludes fields such as, but not limited to: account_id, account_PAN,account_type, brand, expiration_date, spending_limit, billing_address,issuer_name, nickname, loyalty_program_ID, and/or the like.

In one embodiment, the DCB database may interact with other databasesystems. For example, employing a distributed database system, queriesand data access by search DCB component may treat the combination of theDCB database, an integrated data security layer database as a singledatabase entity.

In one embodiment, user programs may contain various user interfaceprimitives, which may serve to update the DCB. Also, various accountsmay require custom database tables depending upon the environments andthe types of clients the DCB may need to serve. It should be noted thatany unique fields may be designated as a key field throughout. In analternative embodiment, these tables have been decentralized into theirown databases and their respective database controllers (i.e.,individual database controllers for each of the above tables). Employingstandard data processing techniques, one may further distribute thedatabases over several computer systemizations and/or storage devices.Similarly, configurations of the decentralized database controllers maybe varied by consolidating and/or distributing the various databasecomponents 819 a-m. The DCB may be configured to keep track of varioussettings, inputs, and parameters via database controllers.

The DCB database may communicate to and/or with other components in acomponent collection, including itself, and/or facilities of the like.Most frequently, the DCB database communicates with the DCB component,other program components, and/or the like. The database may contain,retain, and provide information regarding other nodes and data.

The DCBs

The DCB component 835 is a stored program component that is executed bya CPU. In one embodiment, the DCB component incorporates any and/or allcombinations of the aspects of the DCB that was discussed in theprevious figures. As such, the DCB affects accessing, obtaining and theprovision of information, services, transactions, and/or the like acrossvarious communications networks.

The DCB transforms inputs such as product page checkout request and useridentification input (e.g., 211) via DCB components such asoffer/discount determination component 841 and checkout button embeddingcomponent 842, into dynamic checkout button (e.g., 265) outputs.

The DCB component enabling access of information between nodes may bedeveloped by employing standard development tools and languages such as,but not limited to: Apache components, Assembly, ActiveX, binaryexecutables, (ANSI) (Objective−) C (++), C# and/or .NET, databaseadapters, CGI scripts, Java, JavaScript, mapping tools, procedural andobject oriented development tools, PERL, PHP, Python, shell scripts, SQLcommands, web application server extensions, web developmentenvironments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX &FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools;Prototype; script.aculo.us; Simple Object Access Protocol (SOAP);SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/orthe like. In one embodiment, the DCB server employs a cryptographicserver to encrypt and decrypt communications. The DCB component maycommunicate to and/or with other components in a component collection,including itself, and/or facilities of the like. Most frequently, theDCB component communicates with the DCB database, operating systems,other program components, and/or the like. The DCB may contain,communicate, generate, obtain, and/or provide program component, system,user, and/or data communications, requests, and/or responses.

Distributed DCBs

The structure and/or operation of any of the DCB node controllercomponents may be combined, consolidated, and/or distributed in anynumber of ways to facilitate development and/or deployment. Similarly,the component collection may be combined in any number of ways tofacilitate deployment and/or development. To accomplish this, one mayintegrate the components into a common code base or in a facility thatcan dynamically load the components on demand in an integrated fashion.

The component collection may be consolidated and/or distributed incountless variations through standard data processing and/or developmenttechniques. Multiple instances of any one of the program components inthe program component collection may be instantiated on a single node,and/or across numerous nodes to improve performance throughload-balancing and/or data-processing techniques. Furthermore, singleinstances may also be distributed across multiple controllers and/orstorage devices; e.g., databases. All program component instances andcontrollers working in concert may do so through standard dataprocessing communication techniques.

The configuration of the DCB controller will depend on the context ofsystem deployment. Factors such as, but not limited to, the budget,capacity, location, and/or use of the underlying hardware resources mayaffect deployment requirements and configuration. Regardless of if theconfiguration results in more consolidated and/or integrated programcomponents, results in a more distributed series of program components,and/or results in some combination between a consolidated anddistributed configuration, data may be communicated, obtained, and/orprovided. Instances of components consolidated into a common code basefrom the program component collection may communicate, obtain, and/orprovide data. This may be accomplished through intra-application dataprocessing communication techniques such as, but not limited to: datareferencing (e.g., pointers), internal messaging, object instancevariable communication, shared memory space, variable passing, and/orthe like.

If component collection components are discrete, separate, and/orexternal to one another, then communicating, obtaining, and/or providingdata with and/or to other component components may be accomplishedthrough inter-application data processing communication techniques suchas, but not limited to: Application Program Interfaces (API) informationpassage; (distributed) Component Object Model ((D)COM), (Distributed)Object Linking and Embedding ((D)OLE), and/or the like), Common ObjectRequest Broker Architecture (CORBA), Jini local and remote applicationprogram interfaces, JavaScript Object Notation (JSON), Remote MethodInvocation (RMI), SOAP, process pipes, shared files, and/or the like.Messages sent between discrete component components forinter-application communication or within memory spaces of a singularcomponent for intra-application communication may be facilitated throughthe creation and parsing of a grammar. A grammar may be developed byusing development tools such as lex, yacc, XML, and/or the like, whichallow for grammar generation and parsing capabilities, which in turn mayform the basis of communication messages within and between components.

For example, a grammar may be arranged to recognize the tokens of anHTTP post command, e.g.:

-   -   w3c-post http:// . . . Value1

where Value1 is discerned as being a parameter because “http://” is partof the grammar syntax, and what follows is considered part of the postvalue. Similarly, with such a grammar, a variable “Value1” may beinserted into an “http://” post command and then sent. The grammarsyntax itself may be presented as structured data that is interpretedand/or otherwise used to generate the parsing mechanism (e.g., a syntaxdescription text file as processed by lex, yacc, etc.). Also, once theparsing mechanism is generated and/or instantiated, it itself mayprocess and/or parse structured data such as, but not limited to:character (e.g., tab) delineated text, HTML, structured text streams,XML, and/or the like structured data. In another embodiment,inter-application data processing protocols themselves may haveintegrated and/or readily available parsers (e.g., JSON, SOAP, and/orlike parsers) that may be employed to parse (e.g., communications) data.Further, the parsing grammar may be used beyond message parsing, but mayalso be used to parse: databases, data collections, data stores,structured data, and/or the like. Again, the desired configuration willdepend upon the context, environment, and requirements of systemdeployment.

For example, in some implementations, the DCB controller may beexecuting a PHP script implementing a Secure Sockets Layer (“SSL”)socket server via the information server, which listens to incomingcommunications on a server port to which a client may send data, e.g.,data encoded in JSON format. Upon identifying an incoming communication,the PHP script may read the incoming message from the client device,parse the received JSON-encoded text data to extract information fromthe JSON-encoded text data into PHP script variables, and store the data(e.g., client identifying information, etc.) and/or extractedinformation in a relational database accessible using the StructuredQuery Language (“SQL”). An exemplary listing, written substantially inthe form of PHP/SQL commands, to accept JSON-encoded input data from aclient device via a SSL connection, parse the data to extract variables,and store the data to a database, is provided below:

<?PHP header(′Content-Type: text/plain′); // set ip address and port tolisten to for incoming data $address = ‘192.168.0.100’; $port = 255; //create a server-side SSL socket, listen for/accept incomingcommunication $sock = socket_create(AF_INET, SOCK_STREAM, 0);socket_bind($sock, $address, $port) or die(‘Could not bind to address’);socket_listen($sock); $client = socket_accept($sock); // read input datafrom client device in 1024 byte blocks until end of message do { $input= “”; $input = socket_read($client, 1024); $data .= $input; }while($input != “”); // parse data to extract variables $obj =json_decode($data, true); // store input data in a databasemysql_connect(″201.408.185.132″,$DBserver,$password); // access databaseserver mysql_select(″CLIENT_DB.SQL″); // select database to appendmysql_query(“INSERT INTO UserTable (transmission) VALUES ($data)”); //add data to UserTable table in a CLIENT databasemysql_close(″CLIENT_DB.SQL″); // close connection to database ?>

Also, the following resources may be used to provide example embodimentsregarding SOAP parser implementation:

http://www.xav.com/perl/site/lib/SOAP/Parser.htmlhttp://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide295.htm and other parser implementations:http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.IBMDI.doc/referenceguide259.htm all of which are hereby expressly incorporated byreference.

In order to address various issues and advance the art, the entirety ofthis application for DYNAMIC CHECKOUT BUTTON APPARATUSES, METHODS ANDSYSTEMS (including the Cover Page, Title, Headings, Field, Background,Summary, Brief Description of the Drawings, Detailed Description,Claims, Abstract, Figures, Appendices, and otherwise) shows, by way ofillustration, various embodiments in which the claimed innovations maybe practiced. The advantages and features of the application are of arepresentative sample of embodiments only, and are not exhaustive and/orexclusive. They are presented only to assist in understanding and teachthe claimed principles. It should be understood that they are notrepresentative of all claimed innovations. As such, certain aspects ofthe disclosure have not been discussed herein. That alternateembodiments may not have been presented for a specific portion of theinnovations or that further undescribed alternate embodiments may beavailable for a portion is not to be considered a disclaimer of thosealternate embodiments. It will be appreciated that many of thoseundescribed embodiments incorporate the same principles of theinnovations and others are equivalent. Thus, it is to be understood thatother embodiments may be utilized and functional, logical, operational,organizational, structural and/or topological modifications may be madewithout departing from the scope and/or spirit of the disclosure. Assuch, all examples and/or embodiments are deemed to be non-limitingthroughout this disclosure. Also, no inference should be drawn regardingthose embodiments discussed herein relative to those not discussedherein other than it is as such for purposes of reducing space andrepetition. For instance, it is to be understood that the logical and/ortopological structure of any combination of any program components (acomponent collection), other components and/or any present feature setsas described in the figures and/or throughout are not limited to a fixedoperating order and/or arrangement, but rather, any disclosed order isexemplary and all equivalents, regardless of order, are contemplated bythe disclosure. Furthermore, it is to be understood that such featuresare not limited to serial execution, but rather, any number of threads,processes, services, servers, and/or the like that may executeasynchronously, concurrently, in parallel, simultaneously,synchronously, and/or the like are contemplated by the disclosure. Assuch, some of these features may be mutually contradictory, in that theycannot be simultaneously present in a single embodiment. Similarly, somefeatures are applicable to one aspect of the innovations, andinapplicable to others. In addition, the disclosure includes otherinnovations not presently claimed. Applicant reserves all rights inthose presently unclaimed innovations including the right to claim suchinnovations, file additional applications, continuations, continuationsin part, divisions, and/or the like thereof. As such, it should beunderstood that advantages, embodiments, examples, functional, features,logical, operational, organizational, structural, topological, and/orother aspects of the disclosure are not to be considered limitations onthe disclosure as defined by the claims or limitations on equivalents tothe claims. It is to be understood that, depending on the particularneeds and/or characteristics of a DCB individual and/or enterprise user,database configuration and/or relational model, data type, datatransmission and/or network framework, syntax structure, and/or thelike, various embodiments of the DCB, may be implemented that enable agreat deal of flexibility and customization. For example, aspects of theDCB may be adapted for customized communication between entities. Whilevarious embodiments and discussions of the DCB have been directed todynamic checkout button, however, it is to be understood that theembodiments described herein may be readily configured and/or customizedfor a wide variety of other applications and/or implementations.

The invention claimed is:
 1. A dynamic checkout buttonprocessor-implemented method, comprising: receiving, using one or moredata processors, a product page checkout request from a portable userdevice associated with a user; querying, using the one or more dataprocessors, for information associated with a merchant and the user;performing analytics, using the one or more data processors, on awebsite of the merchant or across the World Wide Web using theinformation queried to generate a result of interest to the user;generating, using the one or more data processors, dynamic imagesrepresenting one or more financial accounts to be embedded into awallet-associated checkout button, wherein the dynamic images comprise avisual indication of card art corresponding to the one or more financialaccounts and a visual indication of the result of interest to the user,wherein the visual indication of the card art includes the card artturning a first color if the corresponding financial account has a highbalance and the card art turning a second color if the correspondingfinancial account has a low balance; transmitting, via the one or moredata processors, the dynamic images to the portable user device; inresponse to receiving the dynamic images: embedding the dynamic imagesinto the wallet-associated checkout button; and, displaying thewallet-associated checkout button with the dynamic images on a displayof the portable user device portable user device.
 2. The method of claim1, wherein the product page checkout request results from a World WideWeb browsing of product listings of one or more merchants.
 3. The methodof claim 1, wherein the dynamic images include a visual indication of athreshold of the one or more financial accounts.
 4. The method of claim3, wherein the threshold is customizable and user specific.
 5. Themethod of claim 4, wherein the threshold is customizable and userspecific based upon access to a wallet account associated with the userand the one or more financial accounts.
 6. The method of claim 5,wherein the wallet account stores the user's profile information,payment methods information, and shipping address.
 7. The method ofclaim 1, wherein the step of performing analytics further comprisesdetermining a maximum cash back and wherein the result of interest tothe user is the maximum cash back.
 8. The method of claim 1, wherein thedynamic image is embedded into a link position in the wallet-associatedcheckout button for display on the display of the portable user device.9. The method of claim 1, wherein the wallet: associated checkout buttonoccupies an area within the display of the portable user device.
 10. Themethod of claim 9, wherein the dynamic images are displayed within thearea occupied by the wallet-associated checkout button.
 11. The methodof claim 1, wherein the product page checkout request and the dynamicimages are transmitted over one or more communications networks.
 12. Themethod of claim 1, wherein the portable user device is a wireless mobilecommunications device.
 13. The method of claim 1, wherein the step ofperforming analytics further comprises determining a historical lowestprice of a product on the website of the merchant and wherein the resultof interest to the user is the historical lowest price of the product onthe website of the merchant.
 14. The method of claim 1, wherein the stepof performing analytics further comprises determining a price of aproduct on the website of another merchant and wherein the result ofinterest to the user is the price of a product on the website of theother merchant.
 15. The method of claim 1, wherein the visual indicationcomprises a message further comprised of text.
 16. The method of claim1, wherein the first color is red.
 17. The method of claim 1, whereinthe second color is green.
 18. The method of claim 1, wherein a lowbalance is a zero balance.